FireFly 3 and PB/DLL - any concerns?

Started by TechSupport, February 27, 2006, 07:59:33 PM

Previous topic - Next topic

JR Heathcote

FireFly already has demo versions of EGRID32 and SIGRID that you can use.  You can access these controls from the "Tools" pallette.

TechSupport

Hi esciarra,

Your suggestions have appeared on this forum from time to time over the last couple of years - especially from FireFly users who have done a lot of Visual Basic programming. To be 100% honest, I have no plans to implement the type of code fixups and automatic spacing that you have suggested. The amount of overhead to implement such a feature is just not feasible. I am also dedicated to using the Scintilla code control and that edit control does not have those features built in.

I do appreciate your suggestions :)  I am also looking forward to getting version 3 completed. It will be a while yet but it is progressing slowly but surely.

Roger Garstang

#2 sounds alright.  QBASIC used to do that.  That combined with an autocomplete would be the biggest improvement.  Something like VB with a popup listbox for variables within a type, etc too.

Can't say I like #3 though.  Over the years I've come to use spaces differently on equals.  When assigning I use a= 2 and when comparing I use IF a = 2 then...  That way I know when either case is used.  It kinda happened over time from languages that assigned by a:= 2 and comparing was a == 2, etc.

I don't like the spaces for functions either.  I like the C++ look since a function is like a variable- MyFunction(firstParam, secondParam, thirdParam)  with only spaces after the commas in the param list.  Spaces are for Subs- MySub firstParam, secondParam, thirdParam

JR Heathcote

Paul,

Put me down as a vote to implement AutoCapitalization, this is really a nifty way to prevent boneheaded coding errors.

JR

Marty Francom

Hello Paul,  
  Haven't heard much about FF 3.0 the last couple of months... I and other customers of FF are anxiously waiting it's debut.  Can you share with us the statis of it's development?

TechSupport

I was a bit slow in coding this summer. A fair amount of the FireFly conversion is complete. Actually, all of the hard stuff has been converted. The user will not see much different in the user interface because I want to keep it consistent with FireFly2.

There is a new code editor (Scintilla) and a new ToolBar Editor.

The code generator is all new and greatly improved for speed.

Lots of internal things are new that will allow me to more quickly build in new features and enhancements.

I hope to start work on the new code librarian for FireFly that will allow users to seemlessly add subs/functions to a library of pre-built code (much like using the FireFly Functions FF_). This way, users can create a set of routines and easily have FireFly include only the needed ones in their project and automatically generate their declares. It will also allow an easy way for fellow FireFly users to share code amongst themselves.

Before you ask... I have no idea when FireFly 3 will even be ready for beta testing. :)  I really don't want to hype FireFly3 in these forums or the PB forums because I know how anxious people get and disappointed when a planned release date (or even an approximate date) is missed. I am following my 3 page roadmap for new FireFly 3 features.

I am just one person and FireFly is so huge and the planned new features are vast. Just the tutorials and documentation alone will be a struggle.

:)

Marty Francom

Paul,
.. I know when it is ready, FF 3.0 will be a stellar product.  You know you can put me down as a customer for FF 3.0 when it is ready.  
.. I will put it on my Santa Claus wish list.
Keep up the great work !

Roger Garstang

I think re-usability will be of great importance too especially in this new FF_Functions type thing and in reusing forms.  Will there by some type of markup used with something like <FormName> and such so when the routines or Forms are loaded the values are replaced with the current Project/Form's name and allow reuse.  That is my biggest annoyance right now is bringing a form or code from a form into a new project from an old and having to manually edit all the code and control names, etc.  It would be really nice to have some type of linking, so when changing a control's name the code is adjusted too, etc.