Latest Entries »

WEBLIGHTS component model

more about component model:
each object will hold an instance iD and guid number, instance is named and guid numbers are will be provided by server side or client side components (both are possible, by default object guid numbers are will utilize client side guid numbers) , this will made an object unique both in client side and server side and you can provide access to them by using two ways : one is named and other one using instance or guid numbers .
is  it ongoing versions will use from sqllight available in webkit browsers?
yes, of course we utilize them when they are exists and will do many things easier but developers don’t have to think about it because engine will decide and utilize this ability when it is exists in the browser, dataset’s have their own built in support for all database commands both in client and server side , for example you have sort and filters and select commands plus  master/detail abilities in client side and server side but you will use from client to use it , based on system optimization dataset will use server or client side (also you can add priority option)
mobile support:
in current version we supported desktop browsers as well, they are able to run in all mobie browsers but you need to use from windows mobile 6.5 or earlier , iphone or android (2.2 or later) and opera mobile is supported but it might have few problems , an special version for ipad (tablets in general) , iphone and android is also is under development, the way you use it is not different with desktop  components, but you might need to do few changes in your page design to made them more sweetable for mobile web.
tab bases in browser abilities:
as i told you before , there are seperation of instances which wlll provide a sandbox arround each page, so, you can have several web pages and load them as you need in the same page instance, you must use standard way of code development if you want to do your custom code which means for example you cannot use from public variables or function in many ways, but it is too easy to use this way because we provided an strait way in client side (which is seams to do a winforms code behind) and you will have easy times to do your javascript client side code.
why just mvc?
we did it as we needed to use it but it is possible to made webforms wrapper or jsp or php wrapper, but we recommend to use our standard way which means mvc , in java mvc for spring and in c# and in php mvc php, thats up to you  but we like our mvc applications more.
which view engine suported in c#?
we recommend you to use only from 3.0 plus c# 4.0 and .net 4 framework and razor view engine, currently system do not provide support on old aspx format and we have no plan to do that so.

which countries or organizations are prohibited to use this software?
we are property of US and European union export restrictions, countries are listed in UN Sanctions for technology and People or companies are not permited to use this software for any governmental and non governmental we know there are no copyright law in this countries
which products are recommended to use this framework?
this framework is sepcailly designed to be used in enterprise applciations but also it is possible to use it in non commercial products, the licenense supports opensource in some cases.
how to start?
you need to start with basics of framework such as using datasets and database components , as well you might need to do something in your entity framework or ORM to provide support of framework.

differnces with atandard MVC frameworks.
this framwork uses from models which are possible to contain several models, like any other MVC like framework models are have the duty of connection to data storage and you can provide MODEL in model but meta model might hold one of many of them, you cannot provide data or any storage in first level of meta model class (see next post to understand the diffrence of meta model)
this is a big advantage and will let you to do your complete data handling for each view by a model
is post back is possible ?
yes, possible but by default we supported ajax supportd codes for framework , you can do it , to redirect  a page you must use a differnent way to redirect a page.
is it possible to control members of page using from servr side?
yes, ofcourse you can do that, there are response provider which will let you to provide Javascript codes which are will run immediately after control leaves from server, there are using from a very easy way to handle codes and that is very similiar to a winform based application, this model is provided using Ryan DOM SandBox Moel (RDSM).
am i able to use from standard framework? yes, but they will only provide post back or manual ajax codes, so, we recommend you to use framework functions versa standard mvc components.
is there support for usercontrols?
yes, this framework is a componnt set but will push you use from special way of coding which is moer categorized and effective.

the engine i am talking about was a dream to me for longtime, it have several reasons because it dislike to have a huge code behind of my forms as well, they will never have a safe result most of times, you have to havea long debug process for each page as well you will have your best times over debuging a non perfect code developer (as most of form developers dont have a good knowledge over web design)
so, i tried many ways to do so, finally i find the best design, mvc is so far most advanced development architecture exists and for a web application, it will produce more efficient code in size and you will have a control over everything and you will have an easy way to develop javascript codes. but it is clear for most of developers we will have a raw component environment plus a non wysiwig environment, so, nothing goes rapid, development cost will muliply many times against webforms or php (which is also more costly than webforms) + you will need people have enough understanding over software architecture.
which way i choosed ? this were clear.
i was a delphi developer for over 14 years, since first versions of turbo pascal I continued this great development environment plus great language at it’s time,  in delphi as you remember you had to do few codes for database and db components had a proxy to connect to each other, you had a dataset or table which were connected to a connection and then a datasource utiltize this dataset to saticefy datar for editors, checkboxes, comboboes, list and grid and it done jobs based on a centralized db access architecture .so, we have something like this.
connection = > Datasets = > datasources = > Dbcomponents (edit,checkbox,combobox etc) in web , we need to receive data from a web server which is holding an application inside and there are no direct connection for clients, so, we might have a webservice or a json data provider for ajax applications, someway, ajax or web service are not good enough, later on i will describe why not!
for most of applications using from old way post back we had different ways to fill grids , edits and so on, they were disconnected to each other so, we had to do a code to connect them or we had some bad ways such as update panel (which i hate it  so much) to update editos from server side, in one word, to do a such of clear product with fast action and ajax action the cost will be so high just because you must to do  a lot of buggy custom codes plus, they will be dirty code and you know what i means if you work in a team environment.

MVC 3.00 Based ERP , interface is in persian langauge : 100% auto generated codes in background!

component set have a componentBase class (exactly constructor in javascript) which all other components should be inherited from it, also we hacan do ve an instance manager which will let you to seperate several copies of different pages using that (this is mostly automatic and will be done through compoonents in client or server side, each component will have a unique guid number + name + container, seperation of several instances of pages are guaranteed by Instances, and then you will have a dataset components starting with connection and then wlconnection which will let dataset to send or receive data via different protocols such as XML (webservices etc) , JSON or Weblights which is more efficient one because it will let server to control page controls and manage it without refresh , all of this send or receive action by default will be handled through a simple datasource path and also you will be able to seperate paths for writing / reading  / select and other actions, by default a dataadapter path will be used.
dataset are having their client side cache model, you will have also cached or non cached data storage in server side ( i named then full state and stateless connections) , you will never need to receive a data twice even if you go to new page or doing custom codes, first and second layer of cache are will be managed without developers custom code (no code needed but also you can customize this actions as well), this components are will receive or send data only when you request it then it means if you have 50000 records loaded and you need first five of them you will only receive first five records.
there are special types of datasets such as recursives (trees etc) which are using from a a provider as middlware but developrs will never be busy with coding for them, ofcourse they  can do their own customize code but normally this is not required to do such complex codes.


Get every new post delivered to your Inbox.