WAS: store SQL command. Now: wishful IDE

[mfstuart]

All,
Actually this brings up something that I've been wanting for some time in
RunRev:
A resource list view or explorer - where I have added and can now see a list
of all and any resource object that I've added for the application.
Such as images, icons, SQL scripts, text files, etc. - I hope you get the
idea.
The Application Browser has some of this, such as stacks, cards, AudioClips,
and VideoClips.
So the list structure is there in the Application Browser. IDE's such as
Eclipse and .NET have this explorer already.
This list structure (object explorer) would facilitate adding and editing of
these objects.
They would be applied to the interface with drag and drop capabilities onto
an object such as a card.

So for right now I have to go through out different menus and palettes to
view these objects.
Maybe in a future version there could be this true IDE - "INTEGRATED"
DEVELOPMENT ENVIRONMENT.

On the other hand, is it possible to build such a palette mentioned above,
in RunRev for RunRev?

Regards,
Mark Stuart


Jim Ault wrote:
> 
> On 12/19/07 5:08 AM, "Ian Wood" <revlist at azurevision.co.uk> wrote:
>> Personally I tend to put really long selects (and AppleScripts) in
>> text fields on a hidden stack, as it makes it extremely easy to edit
>> them in the future.
> 
> Editing custom properties is just as easy as a field (in fact better) by
> doing this:
> 
> Let's say you wanted to store an Applescript in a
> custom property called "useBBEditTextFactory02"
> in a stack, any stack.
> 
> open the stack inspector palette
>    (menu Object:Stack Inspector)
> choose "Custom Properties"
> then click the top "+"
> type "useBBEditTextFactory02"
> click OK
> now the lower pane allows pasting and editing of text
> 
> Then move the palette to the upper left corner of your monitor, grab the
> lower right corner of the palette, drag to make it full screen.
> 
> You now have a gigantic, resizing field.  In fact, you are using a Rev
> field
> that has been placed on the palette stack by the Rev team as part of the
> Development Environment (IDE).  Just copy.paste.edit as normal.
> 
> One downside is that you don't keep the formatting and coloring.
> Another is that you can only look at one property at a time, vs fields
> that
> can be side by side, etc.  I have used dynamic fields in that on close
> field
> become thumbnails, and on enter resize and relocate.
> 
> So if you don't care about the coloring, custom properties are easy to
> edit
> using a real Rev field and they can stay in the main stack.
> 
> Jim Ault
> Las Vegas
> 
> On 12/19/07 5:08 AM, "Ian Wood" <revlist at azurevision.co.uk> wrote:
> 
>> 
>> On 19 Dec 2007, at 12:54, runrev260805 at m-r-d.de wrote:
>> 
>>> My select statement is about 60 lines in size. I created a text
>>> field and put the sql commands in it. Is there a better way to do
>>> this?
>>> Where would you store that statement?
>> 
>> Personally I tend to put really long selects (and AppleScripts) in
>> text fields on a hidden stack, as it makes it extremely easy to edit
>> them in the future. Especially with AppleScript this is handy as you
>> can copy-and-paste between the Rev field and Script Editor, keeping
>> the syntax colouring from Script Editor.
>> 
>> Many people on the list prefer using custom properties, though.
>> 
>> Ian
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
> 
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
> 
> 

-- 
View this message in context: http://www.nabble.com/Where-and-how-do-you-store-SQL-command-tp14416444p14421707.html
Sent from the Revolution - User mailing list archive at Nabble.com.