Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we consider this project retired? #311

Open
andreimoment opened this issue Mar 4, 2016 · 14 comments
Open

Should we consider this project retired? #311

andreimoment opened this issue Mar 4, 2016 · 14 comments

Comments

@andreimoment
Copy link

The last closed issue is from April 20 2015.

There have not been new versions in a very long time.

Does KKBox have an intention to continue development on this project?

Thank you!

@Patta
Copy link

Patta commented Mar 22, 2016

i think its dead, like compass

@selfthinker
Copy link

For a while they had it more prominently on their homepage, no idea why they removed it (it is still on the top of the GitHub wiki homepage). But it is officially dead, read the reasoning behind it.

@selfthinker
Copy link

I just realised that it also states that it is not maintained anymore at the very top of the project's README file.

@andreimoment
Copy link
Author

Thank you, Anika.

I've started using middleman app for newer projects. Seems like I'll be
updating fire.app projects to middlemanapp.
On Sat, Apr 23, 2016 at 3:57 AM Anika Henke notifications@github.com
wrote:

I just realised that it also states that it is not maintained anymore at
the very top of the project's README file.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#311 (comment)

@encosion
Copy link

encosion commented May 5, 2016

Good find @andreimoment, will look into this. Thanks.

@selfthinker
Copy link

Fire.app is only a wrapper around Serve, and that project seems to still be alive. So, anyone who doesn't need the newbie/non-dev friendliness of Fire.app could use Serve instead and wouldn't need to re-write any Fire.app projects. Middleman (and others) works equally well for new projects.
If you need to cater for non-devs, I'm not sure which alternatives there are. Middleman & Co wouldn't fit in that case.

@tka
Copy link
Contributor

tka commented May 5, 2016

Fire.app use a patched Serve, eg. layout system.

https://github.com/tka/serve_ext is the monkey patch

@andreimoment
Copy link
Author

Thank you.

I'll take a look at serve.

I already use middleman for new projects and can testify to its usefulness
;)

On Thu, May 5, 2016 at 9:59 AM tka notifications@github.com wrote:

Fire.app use a patched Serve, eg. layout system.

https://github.com/tka/serve_ext is the monkey patch


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#311 (comment)

@selfthinker
Copy link

selfthinker commented Aug 10, 2016

I recently migrated a personal Fire.app project to Middleman. It was really easy as both apps are quite similar. I thought I'd share the steps I took:

  • Move (nearly) everything under /source (except dotfiles, Gemfile, config.*, README, etc)
  • Set :css_dir, :js_dir and :images_dir correctly in config.rb to match corresponding asset directories
  • Move and rename _layout.html.erb to layouts/layout.erb (i.e. move into folder, rename, remove '.html')
  • (In my case I didn't deal with other layouts, but here is how: https://middlemanapp.com/basics/layouts/)
  • Change all occurrences of <%= render ... into <%= partial ...
  • Change every request.path to current_page.url
  • Move helpers from view_helpers.rb into config.rb into a helpers do block
  • It's not necessary but it's better to change all links to use link_to as that gives you more options and makes things more flexible

There might be more to do for other projects but that was all that was necessary in my case.

@andreimoment
Copy link
Author

Thank you, this is very useful!

@stebdjui
Copy link

stebdjui commented May 24, 2017

Hello,
for all people that searching a newer tool then fire.app:

This project is alive and up to date: https://prepros.io/
Works also fine on a windows machine!

@andreimoment
Copy link
Author

andreimoment commented May 24, 2017 via email

@selfthinker
Copy link

If Prepros works for you or not depends on how you've used fire.app. In my case, having used fire.app for prototypes, it is not a replacement, especially because of the partials and layouts etc.
As far as I know, there just is no drop-in replacement. The one app which comes closest to that is Middleman (see above). The only thing Middleman doesn't have is easy installation by non-technical people (because it came with everything, no need to install anything but fire,app). That is something that Prepros seems to be doing.
For other potential alternatives see http://alternativeto.net/software/fire-app/, although I don't think the list is very helpful for my use case.

@andreimoment
Copy link
Author

Thank you, Anika. Like you, I migrated my process (and some of the old Fire.app projects) to middlemanapp.

It would be nice to have an easy to install replacement but at this point I am used to middleman and the flexibility its ecosystem provides.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants