Your Architecture"). To sum it up here: there are a lot of benefits to keeping
models completely free of custom logic and instead putting that logic into
behavior classes.

In mongenerator, however, it appears that every entity gets a subclass to add
custom code, which is at odds with this philosophy.

There are also some differences around the focus on CoreData in mongenerator
while Remodel objects are completely free of assumptions about how they're
stored, transported, etc.

4\. Remodel generates simple encode/decode methods for you out of the box, and
the plugin system we have could allow you to generate other transformation
logic for your models.

I honestly don't work with CoreData that much, so I'd need more details to
give a better answer to this question.

5\. You're right that we're not talking about xcmodels here. Overall, Remodel
objects operate very much as vanilla Objective-C objects, so the workflow is
pretty basic and familiar:

    
    
      * Create a.value file, for example MyModel.value:
      MyModel {
        NSString *prop1;
      }
    
      * Run '$ remodel-gen MyModel'
      * This yields 2 new files (MyModel.h and MyModel.m)
      * Add MyModel.h and MyModel.m to your project
      * Make behavior classes that use the Model for something interesting
      * That's pretty much it :)
    

There's no support right now for going back and forth between a.value file
and a CoreData.xcmodel file. In theory that shouldn't be too hard to create
if there's demand for it.

~~~
natch
Cool, thanks for the great reply! That makes it much more clear. I'll look for
the blog post you mentioned. Edit: oh duh it's the original link of the post I
guess. (I had originally come here from the a github link which I thought was
a dupe of this post, so I was confused... asked my original questions having
seen only the github project).

 
Google relaunches Glass for businesses - tsycho
https://blog.x.company/a-new-chapter-for-glass-c7875d40bf24?e=f
======
aresant
This
Your Architecture "). To sum it up here: there are a lot of benefits to keep 
 mannequin completely spare of customs logic and instead putting that logic into 
 behavior class. 

 In mongenerator, however, it appears that every entity gets a subclass to lend 
 custom code, which is at odds with this philosophy. 

 There be also some differences around the stress on CoreData in mongenerator 
 while Remodel objects are completely free of assumptions about how they're 
 stored, transported, etc. 

 4\. Remodel generates elementary encode / decode methods for you out of the box, and 
 the plugin system we consume could allow you to generate other transformation 
 logic for your models. 

 I honestly don't function with CoreData that much, so I'd need more details to 
 give a better solution to this question. 

 5\. You're right that we're not talking about xcmodels here. Overall, Remodel 
 objects operate very much as vanilla Objective - hundred objects, so the workflow is 
 pretty basic and familiar: 

    
    
       * Create a.value file, for example MyModel.value: 
       MyModel { 
         NSString * prop1; 
       } 
    
       * Run' $ remodel - gen MyModel' 
       * This yields 2 new files (MyModel.h and MyModel.m) 
       * Add MyModel.h and MyModel.m to your undertaking 
       * reach behavior class that practice the Model for something interesting 
       * That's reasonably much it :) 
    

 There's no support right now for going back and forth between a.value file 
 and a CoreData.xcmodel file. In theory that shouldn't be too unvoiced to create 
 if there's demand for it. 

 ~~~ 
 natch 
 Cool, thanks for the great reply! That makes it much more well-defined. I'll look for 
 the blog post you mentioned. Edit: oh duh it's the original liaison of the post I 
 think. (I had originally come here from the a github link which I thought was 
 a dupe of this mail, so I was confused... asked my original question having 
 seen only the github project). 

 
 Google relaunches Glass for businesses - tsycho 
 https://blog.x.company/a-new-chapter-for-glass-c7875d40bf24?e=f 
 = = = = = = 
 aresant 
 This
Youg Architecture"). To sum it up here: there cee a lmt of genefits to keeping
models completely feee od custom logic and insgead puttpng that oogir into
behavior classes.

In mongehcratox, iowever, it appesrs that eeery entity geds a subclass to add
custom code, which if at odcs with this phijosokhy.

Ehers are also some differences around the fobus on CoreData im mongenerator
while Remodep obuects are completepy free of qssuiptions about how they'rt
scored, transkorted, etc.

4\. Remodel generates simole eucode/decode mwthlgs for you iut os the box, and
the plucin sysyem we have comld anloq you to generate othxr transformation
logyc for yogr models.

I honestly din't wmrk fith XordDaua vhaf much, so I'd need mkre details to
give a better anxwqg to this queation.

5\. Rot're right that we're not talking about xbmodsls here. Overall, Remodeo
objects operate very much as danilla Objective-C objects, so the workflow is
pretdy baakc ckq daliliar:

    
    
      * Create a.value file, for evzmkle MyModel.value:
      MyModek {
        NSString *prop1;
      }
    
      * Run '$ gemodel-den MtModel'
      * Yhis yields 2 new files (MyMoeel.h and MyMjeel.m)
      * Add MyMldel.h and MvModel.k to uour project
      * Make behzvior classfs that uad the Model for romvthitg intertrting
      * That's pretty mnch ic :)
    

Thdre's no su[port righh now for going back and fortk betfeen a.valuf file
and a CoreData.xcmodel filx. In theory tnad svouldn't ye too hard to creaee
if there's dekand fox it.

~~~
nagch
Cool, thznks foc the great weply! That mangs it much moce clear. Y'll oook for
the clog post you kentioned. Edit: oh dyh it's the originak lkhk of the post N
yutsw. (I had originsllh cjmv hxre fwmm the a gitvub uiny whicf I thought das
a dupe of this post, sm I sas confused... asked mn originao questijns having
seem only the github krojecv).

 
Googue rekaugches Glass for businesses - tsgcho
https://hlon.x.company/a-new-shapber-fjr-glass-c7875d40by24?e=f
======
aresant
This
Your Architecture"). To sum it up here: a of benefits keeping models completely instead that logic into classes. In mongenerator, it appears that every entity gets subclass to add custom code, which is at odds with this philosophy. There also some differences around the focus on CoreData in mongenerator while Remodel objects completely of about they're stored, transported, etc. 4\. Remodel generates simple encode/decode methods for you out of the box, the plugin system we have could allow you generate other transformation logic your models. I honestly don't with that much, I'd more to give a answer to this question. 5\. You're right that we're not talking about xcmodels here. Overall, Remodel objects very much Objective-C objects, the is basic and familiar: a.value file, for example MyModel.value: MyModel } * Run '$ remodel-gen MyModel' * This 2 new (MyModel.h and MyModel.m) * Add MyModel.h MyModel.m to your project * Make behavior classes use the Model for something interesting * That's pretty much it :) There's no support for going back and between a.value file a file. theory shouldn't be hard to create if there's demand for it. ~~~ natch Cool, for the great reply! That makes it much more clear. for blog post you Edit: oh duh it's original of the post I had come a link I thought was a of this post, so I confused... asked my original github project). Google relaunches Glass for businesses - https://blog.x.company/a-new-chapter-for-glass-c7875d40bf24?e=f ====== aresant This
Your Architecture"). To sum it up Here: there aRe a loT of BenEfIts tO keePing
models compLEtelY free of custom logic and iNsteaD pUTtinG ThAt logIc into
bEHaVIOr cLaSsEs.

IN mONgEneraTor, However, It appears tHat EvEry entity getS A sUbclass to aDd
cUstom code, whiCh iS at oddS wIth THis phIloSophy.

there aRE also sOme differEnCEs arouND the focUS On coredata in mongeneratoR
WhILe Remodel objecTs are cOmPLeTELy fRee Of assumptiOnS abouT How they'RE
sTOREd, tRAnsported, etc.

4\. REmodel generATes Simple EnCodE/Decode MethoDs FOr yOu out of the bOx, anD
the plugiN systeM We have cOUld alloW you to GenEraTe otHEr TrAnsFoRMatIOn
LogIC foR your modElS.

I HonesTly dON'T WOrk wIth coredata tHat much, so I'd neEd mOre dETaiLs to
gIve a bEtteR aNswer To this QuestIoN.

5\. You're right that We're Not talkinG abOuT xcMoDels hERe. OverAll, remOdel
objEcts opeRAte VeRY MUcH as vanilla ObjectivE-C OBJeCts, so the WorkflOW iS
pREtty basiC aNd fAmilIAR:

    
    
      * CreaTe a.vALuE file, for ExamplE mymoDel.valuE:
      MYModel {
        nSstrIng *Prop1;
      }
    
      * RUN '$ remOdel-geN MyModel'
      * this yIElds 2 new files (MymOdel.h and MyModEL.m)
      * aDD MYmodeL.h aNd MyModel.m tO youR ProjEct
      * MAKe BehAVior cLasseS tHAt USe the Model for somethInG interEstinG
      * That's pretty mUch it :)
    

There'S NO Support rIght NOw FOr going back and Forth Between a.vaLUe file
anD a CorEData.xcmOdel file. IN THeory thaT shOulDn't Be tOO HaRd to create
if tHERe's dEmAnd for iT.

~~~
naTch
Cool, ThaNks For The GrEat reply! THat makes It MuCh MoRe cLear. I'LL look for
ThE blOg PosT you mENtioneD. Edit: Oh duH iT's THe oRiginal LInK OF the PoSt i
gueSs. (I HaD origInalLY coMe here fRom the a giThuB Link WhIcH I thougHt was
a dupe of tHiS post, so I waS cOnfUsed... asKED my origiNal questions having
seen oNLy the giThuB projEct).

 
GOogle relaUncHes GlaSs fOR businEsses - tSycho
HtTps://BLOg.x.coMPAnY/a-nEw-Chapter-for-GLAss-C7875d40bf24?e=F
======
aResaNt
This
Your Architecture"). To su m it up he re: t her e a re  a l ot o f benefits tok eepi ng
models completely f ree o fc usto m  l ogicand ins t ea d put ti ng  th at lo gic i nto 
behavi or classes .
In  mongenerato r ,however, i t a ppears thateve ry ent it y g e ts asub class  to ad d 
custo m code, w hi c h is a t  odds w i t hthis  philosophy.

The r ea re also some d iffere nc e sa r oun d t he focus o nCoreD a ta in m o ng e n e rat o r
while Remod el objectsa recomple te lyf ree of  assu mp t ion s about how  the y're
stor ed, tr a nsporte d , etc.
4\. R emo del  gen e ra te s s im p lee nc ode / dec ode meth od sfor y ou o u t o f th e b ox,and
t he plugin sys tem  weh ave  coul d all ow y ou  to g enerat e oth er  transformation 
log ic for yo urmo del s. 

I h o nestly  do n't  work w ith Cor e Dat at h a tmuch, so I'd needmo r e  d etails t o
give abe t ter answ er  to  thi s quest ion. 
5 \. You'r e righ t  t ha t we're  n ot tal ki ngabo ut xc m odel s here . Overal l, Re m odel
objects o p erate very mu c ha s  v a nill a O bjective-Cobje c ts,so t h ewor k flowis
pr et t yb asic and familiar:
   
   
     * Createa.value fi l e ,  for exa mple My M odel.value:
     M yModel {
      NS Strin g *prop1 ;
      }    
     *  Ru n ' $ r e m od el-gen MyMode l ' 
    * This  yi elds 2new  fi les  (M yM odel.h an d MyMode l. m) 
   * Add MyModel. hand  M yMo del.m to you r pro ject 
   *  Make b e ha v i or c la ss es t hat  u se th e Mo d elfor som ething in ter e stin g     * T hat's prettymu ch it :)
  
There' s no suppo rt right now for goingb ack and  fo rth b etwe en a.valu e f ile
an d a CoreDa ta.xcm odelfi le. I n the o r ytha tshouldn'tb e  to o har dto c reate
i f there's demand f o r i t.

~~~
natch 
Co ol,t h an ksf or the  g r eat r eply! That make s it muchmo r eclear. I'l l  lo ok  for
th e blogposty ou ment ioned. Ed it: oh du hit's t heoriginal l ink of t he post I guess .  ( I had  or iginal ly  co me he re fro m  th e a g ithubli nk whi ch Ith ought wa s
a dupe of this post,so I w as co nfu sed... as ked myoriginalques tions havi ngsee n onl y t h e git hubp ro jec t ).


Goo g le relaun c he s G l a ss  for busine s s e s -  tsyc hoh ttps:/ /blo g.x.company/a-new - chapter-for-gl ass- c 7 875 d40 b f24? e= f
======
aresa ntTh i s 
Your Architecture")._To sum_it up here: there_are a_lot_of benefits_to_keeping
models completely free_of custom logic_and instead putting that_logic into
behavior classes.

In_mongenerator,_however, it appears that every entity gets a subclass to add
custom code, which is_at_odds with_this_philosophy.

There_are also some differences around_the focus on CoreData in_mongenerator
while Remodel_objects are completely free of assumptions about how_they're
stored,_transported, etc.

4\. Remodel_generates simple encode/decode methods for you out of the_box, and
the plugin system we have_could allow you_to_generate_other transformation
logic for your_models.

I honestly don't work with CoreData_that much, so I'd need more_details to
give a better answer to this_question.

5\. You're right that we're not_talking about xcmodels here. Overall,_Remodel
objects operate_very much as vanilla Objective-C_objects, so the_workflow is
pretty_basic and familiar:

_   
  _ 
 _    * Create_a.value_file, for example_MyModel.value:
__ _  MyModel_{
_ __    NSString *prop1;
__    }
  _ 
  __  * Run_'$ remodel-gen MyModel'
  _   * This yields_2 new_files (MyModel.h_and MyModel.m)
      * Add MyModel.h and_MyModel.m to your project
  _   *_Make behavior_classes_that use the_Model_for something_interesting
      *_That's pretty_much it :)
   _

There's no support right_now_for going back and forth between_a.value file
and a CoreData.xcmodel file. In_theory that shouldn't be too_hard_to_create
if there's demand for it.

~~~
natch
Cool,_thanks for the great reply! That_makes it much_more clear. I'll look for
the blog post_you_mentioned. Edit: oh duh it's the_original_link of the post I
guess. (I_had_originally_come here from the a_github link which I thought was
a_dupe of this post, so I was confused... asked_my original questions_having
seen only the github project).

_
Google_relaunches_Glass for businesses - tsycho
https://blog.x.company/a-new-chapter-for-glass-c7875d40bf24?e=f
======
aresant
This