A stakeholder asked me diagrams that explains how the source code of a Codename One app I’m writing works. It’s a generic question about diagrams... and it seems mission impossible to do by hand: currently I’ve already written about 50k lines of code for this app... Do you know any automatic tool that works fine with the sources of a Codename One app to make printable diagrams (any type of diagram that helps to understand how the code works)?
Thank you
If the language is Java, then you can have a lot of UML makers out there
Use IntelliJ to generate class diagram will help if you are using an IDE.
Related
I'm newer in Web developpement (I have modest knowledge about it).
I'm asked in my university-project to develop a webapp that generates a UML class diagram using ReactJS.
I've installed nodeJS, webstorm, I tested a "hello world" code, it works but I don't know how to generate this digram, from where start.
In reality, I've tested the library storm-react-diagram, but I didn't get any result.
Please , someone can help me, orient me or propse me any template, any code that works to be inspired. really I'm lost.
Thanks
Try to check mxgraph or jointjs this two libraries will help you in your project also you need to be more clear specifying your project because it depends if you are going to generate the diagrams by using drag and drop method or something else
I don't know if it's the good place to ask these questions. So if it's not the case sorry for inconvenience.
We are looking for the most adapted tool for our crossplatform mobile project. Before begin to invest time we are testing many crossplatform develeoppement solution ... it's difficult to find the tool where you say Yes it this one !!
Actually we are beginning to test codename one. It looks very promising but we have some doubts and question about features and how we can organize our project :
Do you know if it is possible to separate code and design -> build each "screen of the app" with one xml file to describe components and style and one java class to define behavior and contents(dynamically or not) of these components ?
What about nfc support ? at least for android apps ?
The ui components are not really "sexy" in examples. Do you know if it is possible to load/download or why not buy some more attractive one.
I hope you will be able to answer our questions
Thank you and sorry for my english ...
build each "screen of the app" with one xml file take a look at
https://www.codenameone.com/blog/gui-builder-walkthru.html
What about nfc support ? at least for android apps ? see here
https://www.codenameone.com/blog/native-interface.html
The ui components are not really "sexy" in examples.
https://www.codenameone.com/gallery.html
But overall I would like to suggest you can't get 'that' sexy unless you not try. Don't take it wrong but see the examples submitted by other and what they developed you may get same or more than that if you try.
I hope you will be able to answer Your questions :)
Cheers
Why would a JavaFXPorts/Gluon Mobile application be better than Codename One, JUniversal or Tabris. Google shows these three solutions which made me wonder, were these solutions not good enough? Especially when Codename One claims to be faster than native code. And why would one choose to start a new project and not for example collaborate with the existing solutions?
Codename One predated most of the others but took a rather different path. In fact Codename One's origins predate JavaFX as far as I know.
Codename One was started by mobile guys and as such the VM doesn't try to offer the full JDK. It's small nimble & AOT from the ground up. The whole toolchain was designed for mobile as explained in their VM project: https://github.com/codenameone/CodenameOne/tree/master/vm
Gluon is JavaFX based so it needs the full VM which back in the day relied on RoboVM. The guys from Codename One explained why they didn't go with that in the link above. Gluon now uses OpenJDK which is an interpreter and probably not the best approh for something that's already dog slow on iOS.
FX was designed by desktop people and Codename One was designed by mobile people, the difference in mindset is huge.
Tabris is a server solution and JUniversal is a Microsoft research project that came out much later. It's goals are unclear.
You missed J2ObjC whose goal is library portability and Avian which is an interesting VM. To my knowledge Codename One had a port for it in the past which underperformed.
I am a newbie for PowerBuilder and for Windows application. I have few projects which consists corresponding code in it and after merging all that I get the final product. The problem I am facing right now is that I don't know how to make a setup of my Windows app using PowerBuilder. If I can get step by step procedure with tiny explanation, I will be able to achieve it already. Have tried Google but ended up with complex confusion. I have created the .exe, but that .exe does not work on any other computer. So please guys help me out.
Thanks
There are two parts to creating a setup program for your application: defining the files and other resources that need to deployed, and building those resources into a setup executable package.
For defining files and resources, you've made it impossible for anyone to even take a shot by referring to two very different (but similar origins) versions of the product in your tags: PowerBuilder (aka PowerBuilder Classic) and PowerBuilder.NET. The deployment requirements for apps built from each of these is very different. However, even if we knew, the best advice is to go through the manuals and review what is required of the features of your specific application. (e.g. if you don't use rich text, deploying the files required to support it would be a waste). A generic list is, IMHO, just bad advice.
As far as building a setup package goes, the first decision is which package building software to pick (none comes with PowerBuilder). Any Windows setup package builder should do. I've used InstallShield and Inno, vastly preferring the latter (after many years of using the former). I know you want steps to walk you through, but a walk through is impossible before picking the software, and frankly, walk throughs of these setup building software has been done elsewhere much better than I'd do.
The bottom line is that the answer isn't as simple as you seem to have been hoping, but it is attainable.
Good luck,
Terry.
I'm getting ready to develop my first Silverlight app. It is going to be primarily used by my church for data input but also will need to generate at least one report, ideally in Excel but XML/XSLT is not outside the realm...
It will be Internet facing and will talk to a SQL Server 2008 db for which I will be creating a web service hosted at the ISP (db is also hosted at the ISP). The clients will be a mix of Windows and Mac.
My question specifically relates to the interface architecture. I know MVVM is big for this right now and I'm comfortable with that. I want to get this up fairly quickly (ie- next 3-4 weeks). I've also seen mention of Prism (Composite Application Guidance) and Caliburn. What are anyone's thoughts on these two? The initial version of the app is not going to be huge so I don't imagine it would be overly difficult to refactor a framework into it at a later date.
You are right, if it's your first development on SL, adding the complexity of MVVM won't help you much.
I think a good approach could be to go for something simple (e.g.: the good old Document/View could be just a good start http://msdn.microsoft.com/en-us/library/4x1xy43a(VS.80).aspx, or just breaking in standard layers, UI / BS / DL).
After that development you will have learnt a lot of good stuff, and then you will be able to throw your app and start new bigger challenges using more advanced architectures (about MVVM, a very good web cast: http://blog.lab49.com/archives/2650 it's WPF based most of the concepts can be ported to SL).
Good luck and enjoy for SL development.
Cheers
Braulio
Start with something you are very comfortable with especially if you need to get this up quickly. Follow good coding standards and should not be a problem to refactor later into other frameworks if you get a bigger team.
This is a useful pdf.
I haven't read it in detail yet myself, but this article looks rather useful:
RIA Architecture with Silverlight in mind