F3 Deployment

One of the comments to my earlier posts expressed some concern that a lot of demo code seemed to be all in one file.

That's just because they were quick demos.

F3 supports packages and imports as in Java. So you can divide your application into as many separate files as you like.

The F3 interpreter actually loads F3 classes by means of the Java class loader. So to deploy F3 code you simply archive it in JAR files as in Java and then make such archives accessible to the Java class loader.

Our F3 IDE plugins are also closely integrated with the corresponding Java plugins. There is no special F3 "perspective" or F3 project type. In both Netbeans and Eclipse, you simply use normal Java projects, create packages using the existing Java facilities and then create F3 files in those packages. The normal build process will "do the right thing" and archive your F3 code into the output jar file of your project.

Comments:

F3 sounds fantastic !! When will it be available on java.net ?

Posted by herve on November 26, 2006 at 02:19 AM PST #

Chris, this is killing us! :) These demos are really cool and we're dying to get our mitts on F3. Is there a time frame in which this stuff will be released?

Posted by Ryan J. McDonough on November 26, 2006 at 09:33 AM PST #

This F3 language looks really cool. It seems to be fairly easy to use, but will there be any tool soon that will make it as easy to use as Flash or XAML (look at Interactive Designer)? It sure is fun to code the interface or graphics, but is certainly faster and funnier to just draw it, right? BTW I work with a site created with a visual tool and the code generated by it is hard to maintain :/ and, on the other side, code generated by VE or Matisse is quite nice... So it is possible to make good tool generating source code.

Posted by Wojciech Halicki-Piszko on November 26, 2006 at 08:49 PM PST #

Is it legal to use a "where clause" when building a table? Here, when building the cells of a table:

cells: bind foreach (p in peoplemodel.person where p.name.toLowerCase().contains(peoplemodel.phrase.toLowerCase())) [
TableCell { text:bind p.name },
TableCell { text:bind p.phone },
TableCell { text: bind p.email }
]
I find an easily reproducible error, but when I use the same "where clause" outside of a Table it works just fine. I have code and instructions on how to reproduce if you are interested.

I'm testing the code in your interactive 2D drawing tutorial, btw, so that might be out of date code I'm testing on.

Posted by Andy White on November 26, 2006 at 10:15 PM PST #

Simple and Nice example !

Posted by شات مصري on December 04, 2010 at 07:58 PM PST #

Simple and Nice example !

Posted by شات on December 04, 2010 at 07:58 PM PST #

Simple and Nice example !

Posted by دردشة on December 04, 2010 at 07:58 PM PST #

Simple and Nice example !

Posted by دردشة مصرية on December 04, 2010 at 07:58 PM PST #

Simple and Nice example !

Posted by شات on December 15, 2010 at 03:30 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

user12610627

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today